Easy2Siksha Sample Papers
GNDU Most Repeated (Important) Quesons
B.A./B.Sc. 5th Semester
COMPUTER SCIENCE
(Database Management System & Oracle)
Based on 4-Year GNDU Queson Paper Trend (2021–2024)
Must-Prepare Quesons (80–100% Probability)
SECTION–A (DBMS Fundamentals & Architecture)
1. Database Architecture / Components / Data Independence
Appeared in:
• 2021 (Q1a – Components of DBMS)
• 2023 (Q1 – Detailed System Architecture of DBMS)
• 2024 (Q1 – Logical & Physical Data Independence, DBA Responsibilies)
Probability for 2025: (100%)
Every year’s paper begins with a core DBMS architecture queson — covering
components, levels of abstracon, or data independence. Must prepare all diagrams
and denions.
2. Keys and E–R Model Concepts
Appeared in:
• 2024 (Q2 – Primary, Candidate, Foreign, Super Keys; E–R Diagram Example)
Probability for 2025: (100%)
Newer trend queson — E–R modeling with key denions and example
database designs (e.g., Student Management System). Likely to reappear since it’s
foundaonal for database design.
Easy2Siksha Sample Papers
2025 Smart Predicon Table
(Based on GNDU 2021–2024 Trend Analysis)
No.
Queson Topic
Years
Appeared
Probability for 2025
1
DBMS Architecture / Components / Data
Independence
2021, 2023,
2024
(100%)
2
Keys & E–R Model Concepts
2024
(100%)
2025 GUARANTEED QUESTIONS (100% Appearance Trend)
Top 7 Must-Prepare Topics
1. DBMS Architecture / Components / Data Independence
Easy2Siksha Sample Papers
GNDU Most Repeated (Important) Answers
B.A./B.Sc. 5th Semester
COMPUTER SCIENCE
(Database Management System & Oracle)
Based on 4-Year GNDU Queson Paper Trend (2021–2024)
Must-Prepare Quesons (80–100% Probability)
SECTION–A (DBMS Fundamentals & Architecture)
1. Database Architecture / Components / Data Independence
Appeared in:
• 2021 (Q1a – Components of DBMS)
• 2023 (Q1 – Detailed System Architecture of DBMS)
• 2024 (Q1 – Logical & Physical Data Independence, DBA Responsibilies)
Probability for 2025: (100%)
Every year’s paper begins with a core DBMS architecture queson — covering
components, levels of abstracon, or data independence. Must prepare all diagrams
and denions.
Ans: A Fresh Beginning: The Story of How Data Found Its Home
1. Understanding the Heart of the System – What Is a DBMS?
A Database Management System (DBMS) is like a smart housekeeper for data.
It helps to store data systematically, retrieve it quickly, update it easily, and keep it
safe from unauthorized use.
It acts as a bridge between the user and the database.
Without a DBMS, working with large amounts of data would be like searching for a
needle in a haystack!
But what makes a DBMS so organized and powerful?
That’s hidden inside its Architecture.
Easy2Siksha Sample Papers
2. The Three-Level Architecture of a DBMS – The Design of the Data World
Just like a building has floors — basement, ground, and top — a DBMS also has three
levels of architecture.
This design was suggested by ANSI-SPARC (American National Standards Institute –
Standards Planning and Requirements Committee) to make databases more flexible
and independent.
Let’s explore these levels step by step through our KVU story.
a) Internal Level (Physical Level) – The Basement of Data
At the bottom of our data building is the Internal Level.
Think of it as the basement of the university data center — where all the machines,
servers, and hard drives store the data physically.
Here, data is stored in binary form (0s and 1s).
This level deals with:
• How data is physically stored on disks,
• The structure of files,
• Indexes, and
• How to access or retrieve data efficiently.
For example:
When KVU saves a student’s record, it is stored as electronic signals on a disk. The DBMS
takes care of where and how it is saved — the user doesn’t need to worry about it.
So, this level ensures efficient storage and performance.
b) Conceptual Level (Logical Level) – The Planning Floor
Now, move to the middle floor — the Conceptual Level.
This is like the main blueprint of the entire university data system.
Here, we don’t care how data is stored, but we care about what data is stored and how
it is connected.
It defines the logical structure of the whole database.
At this level, you’ll find:
Easy2Siksha Sample Papers
• Tables (like Student, Course, Teacher),
• Relationships between them (like “Student takes Course” or “Teacher teaches
Course”),
• Constraints (rules like “Roll number must be unique”).
For KVU, the conceptual level says:
"A Student has a Roll No, Name, Department, and Courses. A Teacher teaches Courses,
and each Course has Students enrolled in it."
This level is managed by the Database Administrator (DBA) and is the heart of database
design.
c) External Level (View Level) – The Top Floor (User’s View)
Finally, at the top, we have the External Level, also called the View Level.
This level is like the front office of the university — where different people see only what
they need.
For example:
• A student can view his marks, timetable, and fees.
• A teacher can view subjects, attendance, and student lists.
• The principal can view reports and overall results.
Each user sees data in a customized way — their own “window” into the database.
So, the External Level focuses on how users view and interact with data, hiding the
complexity underneath.
In Short:
Level
What It Represents
Example (KVU)
External
User’s View of Data
Student or Teacher Portal
Conceptual
Logical Design of Entire
Database
Database schema with tables &
relationships
Internal
Physical Storage of Data
Data saved on disk or server
This 3-level structure ensures that each part of the system focuses on its own job —
making the database flexible, secure, and easy to manage.
Easy2Siksha Sample Papers
3. The Components of DBMS – The Team That Makes It Work
Now that you know the structure of a database, let’s meet the “team” behind it — the
main components of a DBMS.
Just like a university runs smoothly because of teachers, clerks, and administrators — a
DBMS also works efficiently because of its major components.
1. DBMS Engine (or Storage Manager)
This is the brain of the DBMS.
It stores data, retrieves it when needed, and manages all interactions with the physical
storage.
It includes modules like:
• File Manager (handles storage files),
• Buffer Manager (manages memory),
• Transaction Manager (handles transactions), and
• Recovery Manager (restores data after a crash).
It ensures that your data is safe and consistent even when multiple users access it.
2. Database Schema and Data Dictionary
A schema is like the blueprint or design of the database.
A data dictionary is like the library that contains all information about tables, columns,
data types, and relationships.
It’s where the DBMS keeps all “metadata” — data about data.
For example, if someone asks, “What fields does the Student table have?” — the data
dictionary gives the answer.
3. Query Processor
The query processor is like a translator.
When a user types a query in SQL (for example, SELECT Name FROM Student WHERE
Easy2Siksha Sample Papers
RollNo = 5;), the query processor translates it into low-level instructions that the DBMS
can understand and execute.
It consists of:
• Query Parser (checks for errors),
• Query Optimizer (chooses the fastest way to execute the query), and
• Query Executor (actually runs the query).
4. Transaction Manager
Imagine 100 students paying fees online at the same time. The DBMS must ensure that
every transaction happens fully — or not at all.
That’s where the Transaction Manager comes in. It maintains ACID properties —
• Atomicity: All or none rule,
• Consistency: Data remains accurate,
• Isolation: No interference between transactions,
• Durability: Data remains safe even after failures.
5. Database Administrator (DBA)
The DBA is like the principal of the database world.
They manage user access, backups, recovery, performance tuning, and security.
Their responsibilities include:
• Installing and maintaining the DBMS software,
• Designing the database schema,
• Managing user permissions,
• Taking regular backups, and
• Monitoring performance.
6. Users
Finally, there are the users — the people who interact with the database.
There are three types:
1. End Users – students, teachers, customers, etc.
Easy2Siksha Sample Papers
2. Application Programmers – who create software to use the database.
3. Database Administrators (DBAs) – who maintain it.
4. Data Independence – The Superpower of DBMS
One of the best things about a DBMS is Data Independence — the ability to change one
level of the database without affecting the other levels.
There are two types of data independence:
1. Logical Data Independence
This means we can change the conceptual structure of the database without affecting
user views.
For example:
If KVU adds a new field “Scholarship Status” to the Student table, students’ existing
portals will still work fine. The user view doesn’t change.
It’s like renovating the middle floor of a building without affecting what’s visible to the
people on the top floor.
2. Physical Data Independence
This means we can change the physical storage of data without changing the conceptual
schema.
For example:
If KVU shifts data from one server to another or changes the storage format, the logical
structure (tables, columns) remains the same.
Users and programmers don’t need to modify their queries.
Why Data Independence Matters
It makes databases:
• Flexible – easy to modify and expand,
Easy2Siksha Sample Papers
• Stable – changes don’t break systems, and
• Efficient – allows better performance tuning without user disruption.
5. Bringing It All Together – The Beauty of a Well-Built Database
By the end of the story, KVU’s data world became perfectly organized.
The students were happy because they could easily check their marks.
The teachers were relieved because attendance and grading became smooth.
The principal smiled — finally getting complete reports in seconds!
All thanks to the DBMS — a system built on a strong architecture, powered by well-
defined components, and protected by the magic of data independence.
6. Summary Table
Concept
Meaning
Example
DBMS Architecture
Structure with 3 levels: External,
Conceptual, Internal
Different views for student,
teacher, admin
Internal Level
Physical storage of data
Data saved on disks
Conceptual Level
Logical structure of database
Tables and relationships
External Level
User view of data
Student’s mark view
Components of
DBMS
Parts that make DBMS work
Query processor, storage
manager, etc.
Logical Data
Independence
Change in schema without
affecting views
Adding a new field
Physical Data
Independence
Change in storage without
affecting schema
Moving data to another
server
Final Thought
A DBMS is not just a technical tool — it’s a beautiful system designed to make data
meaningful, manageable, and magical.
Just like a well-run university, it brings order to chaos, efficiency to effort, and
intelligence to information.
And that’s the real story of Database Architecture, Components, and Data
Independence — a story where every piece of data finds its perfect place.
Easy2Siksha Sample Papers
2. Keys and E–R Model Concepts
Appeared in:
• 2024 (Q2 – Primary, Candidate, Foreign, Super Keys; E–R Diagram Example)
Probability for 2025: (100%)
Newer trend queson — E–R modeling with key denions and example
database designs (e.g., Student Management System). Likely to reappear since it’s
foundaonal for database design.
Ans: Keys and E–R Model Concepts
Imagine you walk into a giant library. There are thousands of books stacked neatly on
shelves. Now, suppose you want to find one specific book—say “Introduction to
Databases”. Without a catalog system, you’d be lost. But the librarian smiles and says:
• “Tell me the ISBN number, and I’ll fetch it instantly.”
That ISBN number is like a key—a unique identifier that helps locate exactly what you
need.
Now, imagine the library itself is being designed from scratch. The architect draws a
plan: shelves (entities), books (attributes), and relationships (which shelf holds which
book). That plan is like an E–R Model—a blueprint of how data is organized and
connected.
This is the story of Keys and the E–R Model—two foundational concepts in database
design.
Part 1: Keys in Databases
1. What are Keys?
In databases, keys are attributes (or sets of attributes) that help identify records
uniquely and establish relationships between tables.
Think of keys as identity cards for data. Just as every citizen has a unique Aadhaar
number, every record in a database needs a unique identifier.
Easy2Siksha Sample Papers
2. Types of Keys
(a) Primary Key
• A primary key uniquely identifies each record in a table.
• It cannot be NULL and must be unique.
• Example: In a Students table, Roll_No can be the primary key.
sql
CREATE TABLE Students (
Roll_No INT PRIMARY KEY,
Name VARCHAR(50),
Age INT
);
(b) Candidate Key
• A table may have multiple attributes that can serve as a primary key.
• These are called candidate keys.
• Example: In the Students table, both Roll_No and Aadhaar_No could uniquely
identify a student. One of them is chosen as the primary key, the others remain
candidate keys.
(c) Alternate Key
• The candidate keys that are not chosen as the primary key are called alternate
keys.
• Example: If Roll_No is chosen as the primary key, then Aadhaar_No becomes an
alternate key.
(d) Foreign Key
Easy2Siksha Sample Papers
• A foreign key is an attribute in one table that refers to the primary key of another
table.
• It establishes a relationship between two tables.
• Example: In a Marks table, Roll_No can be a foreign key referencing the Students
table.
sql
CREATE TABLE Marks (
Roll_No INT,
Subject VARCHAR(50),
Marks INT,
FOREIGN KEY (Roll_No) REFERENCES Students(Roll_No)
);
(e) Composite Key
• A composite key is formed by combining two or more attributes to uniquely
identify a record.
• Example: In a Course_Registration table, the combination of Roll_No and
Course_ID can act as a composite key.
(f) Super Key
• A super key is any set of attributes that can uniquely identify a record.
• Every primary key is a super key, but not every super key is a primary key.
• Example: {Roll_No}, {Roll_No, Name}, {Roll_No, Age} are all super keys, but only
{Roll_No} is the primary key.
3. Why Keys are Important
• Uniqueness: Prevents duplicate records.
• Relationships: Connects tables meaningfully.
• Integrity: Ensures data consistency.
• Efficiency: Speeds up searching and indexing.
Part 2: The Entity–Relationship (E–R) Model
1. What is the E–R Model?
The Entity–Relationship Model is a conceptual blueprint for designing databases. It was
introduced by Peter Chen in 1976.
It helps us visualize data as:
• Entities (things we want to store information about).
• Attributes (properties of those entities).
• Relationships (how entities are connected).
Easy2Siksha Sample Papers
Think of it as the architect’s plan before constructing a building.
2. Components of the E–R Model
(a) Entities
• An entity is an object or thing in the real world that we want to store data about.
• Example: Student, Teacher, Course.
• Represented as rectangles in ER diagrams.
(b) Attributes
• Attributes are properties of entities.
• Example: A Student entity may have attributes: Roll_No, Name, Age.
• Represented as ovals in ER diagrams.
Types of Attributes:
• Simple: Cannot be divided (e.g., Age).
• Composite: Can be divided (e.g., Full Name → First Name + Last Name).
• Derived: Can be calculated (e.g., Age from Date of Birth).
• Multivalued: Can have multiple values (e.g., Phone Numbers).
(c) Relationships
• A relationship shows how entities are connected.
• Example: Student “enrolls in” Course.
• Represented as diamonds in ER diagrams.
Types of Relationships:
• One-to-One (1:1): One student has one library card.
• One-to-Many (1:N): One teacher teaches many students.
• Many-to-Many (M:N): Students enroll in many courses, and courses have many
students.
3. Keys in the E–R Model
• Primary Key: Uniquely identifies an entity (e.g., Roll_No for Student).
• Foreign Key: Connects entities (e.g., Course_ID in Enrollment table).
• Composite Key: Used in many-to-many relationships (e.g., Roll_No + Course_ID).
4. Example of an E–R Diagram
Imagine designing a University Database:
• Entities: Student, Course, Professor.
Easy2Siksha Sample Papers
• Attributes:
o Student: Roll_No (PK), Name, Age.
o Course: Course_ID (PK), Title, Credits.
o Professor: Prof_ID (PK), Name, Department.
• Relationships:
o Student “enrolls in” Course (M:N).
o Professor “teaches” Course (1:N).
The ER diagram would show rectangles (entities), ovals (attributes), and diamonds
(relationships), with keys underlined.
Storytelling Illustration
Let’s imagine a real-life scenario.
A university wants to build a database. The designer asks:
• “Who are the main entities?” → Students, Courses, Professors.
• “What are their attributes?” → Students have Roll_No, Name, Age. Courses have
Course_ID, Title. Professors have Prof_ID, Department.
• “How are they related?” → Students enroll in courses, professors teach courses.
Now, the designer draws an E–R diagram. Roll_No, Course_ID, and Prof_ID are chosen
as primary keys. The Enrollment table uses a composite key (Roll_No + Course_ID).
Relationships are mapped using foreign keys.
By the end, the university has a clear blueprint of its database—thanks to keys and the
E–R model.
Why the E–R Model Matters
1. Clarity: Provides a visual representation of data.
2. Communication: Helps developers, clients, and stakeholders understand the
system.
3. Foundation: Serves as the first step before creating relational tables.
4. Error Reduction: Identifies problems early in design.
A Metaphor to Remember
Think of building a city:
• Entities are the buildings (Student, Course, Professor).
• Attributes are the details of each building (height, color, purpose).
• Relationships are the roads connecting buildings.
• Keys are the addresses that help you find the right building.
Easy2Siksha Sample Papers
Without keys, you’d get lost. Without an E–R model, the city would be chaotic. Together,
they create order and meaning.
Conclusion: The Blueprint and the Keys
• Keys are the unique identifiers that ensure data integrity and connect tables.
• E–R Models are the blueprints that show how entities, attributes, and
relationships fit together.
Together, they form the foundation of database design. Keys give precision, while the
E–R model gives vision.
“This is only a part of the preparation journey.
For full access to repeated questions and detailed answers,
purchase our Premium Papers and boost your chances of scoring
higher!”
